As you probably know, THINK C and MPW have facilities for marking interesting parts of source code. You can make a selection and hit command-M to mark it. From then on it will show up in a menu that you get at by Command-clicking in the title bar of THINK C window, or the Mark menu in MPW. What if you want to mark every function name in the file? You could be careful to mark each function as you type it in, but after some cuts and pastes, the markers can get confused, and take you to different parts of the file by mistake. Don’t ask me why. So you say, how can this be improved?
Enter Marker. No, it’s not an INIT or a CDEV, it’s not even a desk accessory. It’s an application that is System 7 friendly, and runs in a 64k partition. It also runs under System 6.0.5 or newer.
Marker takes a source file created in THINK C or MPW, parses the C source code, and marks each function name it comes across (not the prototypes, only the actual function where it’s defined). You run it, and through a standard get file dialog, you select the file or folder, and away it goes. Most files are marked in less than a second. The next time you open the file in the THINK C editor or MPW, all of the function names in the file will be there when you command-click in the title bar (THINK C), or look in the Mark menu (MPW). It’s that simple.
Standard get file - what a pain! OK, you can also drag files onto the Marker ICON in the finder to have them be marked. Marker will run, mark the file(s), and quit. If you don’t feel like shift clicking all of those files, or you have files in multiple levels of folders, drag a folder onto Marker. That will cause it to mark every function in every THINK C or MPW source file (it also checks in the headers) in the folder, and all folders within it, and so on. You can also drag more than one folder onto Marker. Marker even works in the background when there are more than one files being marked, not that there’s that much time to do anything.
Marks can be in either alphabetical order or file order. Since THINK C automatically orders them alphabetically, I prepend numbers to the function names to preserve file order if that is the chosen marking method. The method is specified via a check box in the get file dialog or by holding the option key down when dragging files or folders onto the Marker icon. MPW gives you the option in its Mark menu, so just mark alphabetically for MPW stuff.
If you exclusively work in either MPW or THINK C, you can have Marker only mark their files, and ignore others. This is done by editing a resource in the application. The resource type, 'CrTr' contains a list of creator types that you want Marker to allow. The default ones are 'KAHL' for THINK C, and 'MPS ' for MPW. If you want others, append them to the list. If you don't want one of them, remove it from the list. You can edit this easily with ResEdit or Resorcerer.
I dragged the entire Think Class Library 1.1 folder onto Marker (over 200 files), and it took less than a minute to mark it.
The best thing about Marker is its price - only $49.95! OK, sorry, it’s FREE. You can use it, love it, hate it, or simply tease your friends with it, but by all means try it. If you feel like it, drop me a note or post card as to what you think or would like to see added to Marker. I’d appreciate it.
I have been using this program to mark files in various projects I am working on, and have had no problems or lost data. However, since this is a Beta release, and you're never certain of bug-free code, if you find a bug, please try to reproduce it a few times and let me know exactly how to find it. If functions are not marked properly, or non functions are marked, send me the file that was marked improperly. If you want to remove any sensitive parts of it, that's fine, but be sure leave enough so the bug shows up! My address (electronic and otherwise) are at the end of this document.
Modification History:
1.0ß1
Initial release.
1.0ß2
Previous versions did not preserve the original modification date of the files being marked. This caused unnecessary recompilations and general confusion when trying to use modification dates as a way to track source file updates. Now, the modification date is left unchanged after adding the markers.
Added a "Mark Folder" button to the get file so that whole folders can be marked from the get file dialog. Thus, users under system 6 can easily mark many files.
Added a FlushVol after the whole folder is done being marked.
1.0ß3
1.0ß2 marked prototypes as well as function themselves. This version does not mark prototypes, but correctly marks all functions (old style and new), as well as class methods.
Now marks can be in either alphabetical order or file order. Since THINK C automatically orders them alphabetically, I prepend numbers to the function names to preserve file order if that is the chosen marking method. The method is specified via a check box in the get file dialog or by holding the option key down when dragging files or folders onto the Marker icon.
1.0ß4
Added the 'CrTr' resource to allow Marker to mark different TEXT files from various creators. This allows users of THINK C or MPW or both to take advantage of Marker.
Now Marker ignores #define'd things. Macros and other things in #define's will not be marked.
1.0ß5
Fixed a bug that marked functions declared as pointers as empty strings (short *aFunc(...) got marked as "").
Marking class methods now includes the method name with the function name.
1.0ß6
Fixed a bug that marked preprocessor directives (like #defines) when they looked like functions and were on the first line of the file. (e.g. #pragma options(defer_adjust))
